-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Basic implementation of Caching Middleware #39
Conversation
8746c28
to
4a7e7ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in addition to the requested changes in the comments
- Update developer docs with notes on what type of cache is used
- Add new architecture docs for how the cache works, and how it modifies the proxy request flow, and how to debug it when something goes wrong
- finish out todo’s
- add docs on how to invalidate the cache (either all keys or for specific methods)
- add e2e integration test in main_test.go that verifies when a cacheable request is sent to the proxy service it does get cached in the local docker redis
305b1c5
to
d4c21ed
Compare
@evgeniy-scherbina we'll want to be able to flip the cache on or off via an environment variable (e.g. some if block in those middleware that is checked first before running any of the caching specific code and hands off to the next handler if the cache is configured to be disabled) in cases where there is a bug that is safer / faster to bypass in production by disabling the cache, and to allow debugging to correctly triage if any observed issues with the proxy are related to the caching code paths |
dfaec36
to
d0868b8
Compare
ed69b88
to
7066f92
Compare
5e6ad5e
to
589b2e4
Compare
589b2e4
to
9ff12c4
Compare
03ee2ff
to
00ed140
Compare
there were conflicts |
Documentation: https://github.com/Kava-Labs/kava-proxy-service/blob/yevhenii/cache/architecture/CACHING.md